home *** CD-ROM | disk | FTP | other *** search
- KILLDIR version 4.0
- This program was re-written in 'C' and no longer includes the
- source code in the archive library, KILLDIR.ARC, since the 'C' program
- calls assembler modules to do functions such as changing directories, etc.
- Without the assembler modules in my library, you could not re-compile this
- anyway, and my library is set up to work with Microsoft 'C' only.
-
- CHANGES:
- The major changes from previous versions of KILLDIR include:
- 1. The program contains a "recursive" feature which will delete the
- indicated directory and as many sub-sub directories as exist under the
- target directory.
- 2. The program now only prompts once to ask permission to delete
- read-only files. Previous versions asked permission for each file it found.
-
- SYNTAX:
- 1. Don't include the \ (root symbol) before the directory name
- to be killed, (i.e., use KILLDIR LEVEL1, not KILLDIR \LEVEL1).
-
- 2. You CANNOT be in the directory you are trying to delete. You
- must be somewhere in the directory tree above the branch you are trying
- to delete. For example, if you want to kill \LEVEL1, you should be in
- the root (\), NOT in \LEVEL1.
-
- If you have a subdirectory structure as follows, the commands below
- it would have the listed effects.
-
- \(root)---\LEVEL1---\LEVEL2---\LEVEL3---\LEVEL4
- | | |
- filea
- fileb
- filec
- \LEVEL1\LEVEL1A
- |
- filed
- filee
- \LEVEL1\LEVEL1A\LEVEL1B
-
-
- Your location is: \ (this is the root)
- KILLDIR LEVEL1
- This command would kill the subdirectories starting at \LEVEL1
- and including: \LEVEL1, \LEVEL1\LEVEL1A, & \LEVEL1\LEVEL1A\LEVEL1B
- and the files including: filea, fileb, filec, filed, & filee. These
- files would be deleted even if they were read-only files.
-
- Your location is: \ (this is the root)
- KILLDIR LEVEL2
- This command would remove the subdirectories & files starting
- at \LEVEL2.
-
- Your location is: \ (this is the root)
- KILLDIR LEVEL1\LEVEL1A
- This command would kill the subdirectories starting at
- \LEVEL1\LEVEL1A, through \LEVEL1\LEVEL1A\LEVEL1B; and files
- filed and filee.
-
-
- If you enter the path incorrectly, (and the path is relative to your
- position in the directory tree), you will get an "invalid path" message.
- For example, if you are in \LEVEL2 and specify:
- KILLDIR LEVEL1
- You will get the error message "invalid path", it will beep at you
- and it will end. Simply "CD \" and re-enter the command as "KILLDIR LEVEL1".
-
- HOW IT WORKS:
-
- KILLDIR works by changing into the directory you specified,
- for example CD'ing into LEVEL1, deleting the files in LEVEL1, checking
- for and deleting any READ/ONLY files there, checking for sub-subdirectories,
- changing into sub-subdirectories, and repeating the process. Once I
- get to the bottom of the tree, for example down to \LEVEL1\LEVEL1A\LEVEL1B,
- I start CD'ing back up and removing the now empty directories as I come
- back up until I reach your starting point.
- I also try to put you back in the directory you were occupying when
- you started KILLDIR. If you are in LEVEL2, for example, when KILLDIR
- exits, you are put back into LEVEL2.
- If you have any problems, you can write to me at the following
- address:
- Amy J. Goebel
- #702
- 5903 Mt. Eagle Dr.
- Alexandria, VA 22303
- If you have a modem, you can also reach me at a remote bulletin
- board system where I work. The number is (703)756-6109.
-
-
-
- ----------------end-of-author's-documentation---------------
-
- Software Library Information:
-
- This disk copy provided as a service of
-
- The Public (Software) Library
-
- Disks in the library are updated monthly.
- For a copy of the latest monthly software library newsletter
- and a list of the 800+ disks in the library, call or write
-
- The Public (Software) Library
- P.O.Box 35705 K
- Houston, TX 77235-5705
- (713) 721-6104
-
- We are not the authors of this program, nor are we associated
- with the author in any way other than as a distributor of the
- program in accordance with the author's terms of distribution.
-
- Please direct shareware payments and specific questions about
- this program to the author of the program, whose name appears
- elsewhere in this documentation. If you have trouble getting
- in touch with the author, we will do whatever we can to help
- you with your questions. All programs have been tested and do
- run. To report problems, please use the form that is in the
- file PROBLEM.DOC on many of our disks or in other written for-
- mat with screen printouts, if possible.
-